Closed
Bug 546479
Opened 15 years ago
Closed 15 years ago
confusion of From headers with multiples email addresses/account
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: julien.t43+mozilla, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
I'm currently using many email addresses (gmail with alias, otherinbox with alias, others) with Thunderbird/Macos.
Sometimes, I send a email with address A and recipient receives from address B.
It seems to stay the same provider (A@gmail to B@gmail), not sure about that. It maybe related to multiple identities on one account.
It happens mostly when using gpg signature with enigmail (Case 2)
It happens once with no signature/encryption (Case 1)
*** Case 1
Both address are multiple identities of one account.
Sent message (in sent-mail) has:
>>>
Message-ID: <XXXX.30300@gmail.com>
Date: Mon, 15 Feb 2010 18:55:05 +0100
From: <A@gmail>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: <recipient@>
Subject: <ABCDEF>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
<<<
I received an automated response with these headers
>>>
Delivered-To: <B@gmail.com>
Received: from xxx.com (unknown [10.63.220.6])
by mail.xxx.com (Postfix) with ESMTP id D3B77B3A71
for <B@gmail.com>; Mon, 15 Feb 2010 18:58:23 +0100 (CET)
X-Priority: 3 (Normal)
From: <recipient@>
To: <B@gmail.com>
Message-ID: <XXXX@XXX.com>
Date: Mon, 15 Feb 2010 18:58:17 +0100
X-MIMETrack: Serialize by Router on ITLINNS1/AEB_LIN/ACER(Release 7.0.3FP1|February 24, 2008) at
02/15/2010 06:58:22 PM
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64
<<<
*** Case 2
The two addresses come from 2 different accounts.
with gpg signature, I got (old test):
Sending email without signature:
>>>
Message-ID: <4AA22160.9060901@gmail.com>
Date: Sat, 05 Sep 2009 10:29:20 +0200
From: <A@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: <recipient>
Subject: test w/o sign
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<<<
received
>>>
Return-Path: <B@gmail.com>
Delivered-To: <recipient>
[...]
Received: [...]
Message-ID: <4AA22160.9060901@gmail.com>
Date: Sat, 05 Sep 2009 10:29:20 +0200
From: <B@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: <recipient>
Subject: test w/o sign
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<<<
Sending with signature
>>>
Message-ID: <4AA22178.5010504@gmail.com>
Date: Sat, 05 Sep 2009 10:29:44 +0200
From: <A@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: <recipient>
Subject: test w sign
X-Enigmail-Version: 0.95.7
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature";
boundary="------------enig65E57EA067840508872BE855"
<<<
received
>>>
Return-Path: <B@gmail.com>
Received: [...]
Message-ID: <4AA22178.5010504@gmail.com>
Date: Sat, 05 Sep 2009 10:29:44 +0200
From: <B@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: <recipient>
Subject: test w sign
X-Enigmail-Version: 0.95.7
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature";
boundary="------------enig65E57EA067840508872BE855"
<<<
Re-test with 3.0.1:
Sent:
>>>
Message-ID: <4B79CB56.1010004@gmail.com>
Date: Mon, 15 Feb 2010 23:31:50 +0100
From: <A@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: <recipient>
Subject: test sign+crypt
X-Enigmail-Version: 1.0
Content-Type: multipart/encrypted;
protocol="application/pgp-encrypted";
boundary="------------enig63B633E55000D97ED2EB9335"
<<<
Received
>>>
Return-Path: <B@gmail.com>
Received: [...]
Message-ID: <4B79CB56.1010004@gmail.com>
Date: Mon, 15 Feb 2010 23:31:50 +0100
From: <B@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: <recipient>
Subject: test sign+crypt
X-Enigmail-Version: 1.0
Content-Type: multipart/encrypted;
protocol="application/pgp-encrypted";
boundary="------------enig63B633E55000D97ED2EB9335"
<<<
Reproducible: Always
Comment 1•15 years ago
|
||
Does this problem occur also in Safe Mode (https://support.mozillamessaging.com/en-US/kb/Safe+Mode)?
Comment 2•15 years ago
|
||
> Sending email (snip)
> From: <A@gmail.com>
> Received
> From: <B@gmail.com>
What SMTP server did you use for mail sending? SMTP server of Gmail?
If yes, which usename did you use for SMTP auth(login)? A@gmail.com? B@gmail.com?
If Gmail's SMTP and username=B@gmail.com, do next (A) and (B).
(A) Set "Sent" folder for the identity "XYZ" of "Local Folders", send mail to your other mail address you have, check mail source of copy of sent mail data in "XYZ" of "Local Folders", check mail source of sent mail in [Gmail]/Sent Mail(if Gmail IMAP) or Sent Mail FOLDER(at Gmail Web), and check mail source of delivered mail.
As you saw in comment #0, once mail data is passed to SMTP server, mail client(Tb) is absolutely irrelevant to mail header data transfered by Gmail.
(B) Read next.
> Gmail's Settings/Accounts and Import, Sending mail as:, Lern more
> http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=22370
> Bug summary : confusion of From headers (snip)
Confusion by whom? You, aren't you? (not Tb, not Gmail, ...)
Reporter | ||
Comment 3•15 years ago
|
||
ok. my miss, you are right wada.
That's gmail server which revert From to user used for smtp authentication. It also removed any alias used, even if it is the good user (A+something@).
Not sure, it was in place before but I'm ok with this security settings.
thanks for the point.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Resolution: FIXED → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•